Skip to content

Conversation

@czechboy0
Copy link
Contributor

Motivation

This package doesn't have any library products that would need to maintain API stability, so we don't need to run the CI.

We only have _OpenAPIGeneratorCore, which is underscored and not expected to be API stable (so it can only be used using an exact: "..." constraint). But we don't want to fail CI when we change that API (right now it's introducing noise in: #627)

Modifications

Disable API breakage check.

Result

Disabled that CI step.

Test Plan

N/A

@simonjbeaumont
Copy link
Collaborator

Should we instead keep it but relax the rule. Be good to know when we're breaking the underscored library product?

@czechboy0
Copy link
Contributor Author

We don't even attempt to keep the underscored library's API stable, it's purely for experimentation with in-memory codegen. So I don't particularly care when we break its API.

@czechboy0 czechboy0 merged commit 3711876 into apple:main Oct 7, 2024
24 checks passed
@czechboy0 czechboy0 deleted the hd-disable-api-breakage-ci branch October 7, 2024 15:20
@czechboy0 czechboy0 added the semver/none No version bump required. label Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

semver/none No version bump required.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants